Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

citizen logout redirection handled in multiroot tenant #1633

Merged
merged 2 commits into from
Oct 23, 2024

Conversation

mithunhegde-egov
Copy link

@mithunhegde-egov mithunhegde-egov commented Oct 23, 2024

citizen logout redirection handled in multiroot tenant

Summary by CodeRabbit

  • New Features

    • Enhanced logout functionality that conditionally redirects users to the citizen login page based on tenant settings.
  • Bug Fixes

    • Improved handling of logout process to ensure a smoother user experience.

@mithunhegde-egov mithunhegde-egov requested a review from a team as a code owner October 23, 2024 06:50
Copy link
Contributor

coderabbitai bot commented Oct 23, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request modify the handleOnSubmit function within the StaticCitizenSideBar component. The updated implementation introduces a conditional check for multi-root tenants before executing the logout process. If the condition is met, the user is redirected to the citizen login page after logging out; otherwise, the user is logged out without redirection. The redirectToLoginPage function remains unchanged but is still present in the code.

Changes

File Change Summary
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js Modified handleOnSubmit to include a conditional check for Digit.Utils.getMultiRootTenant() affecting logout behavior and user redirection. redirectToLoginPage remains unchanged but is present.

Possibly related PRs

Suggested reviewers

  • jagankumar-egov

🐇 In the sidebar where users roam,
A logout dance leads them home.
With checks for tenants, swift and bright,
Redirects guide them to the light.
Hopping through code, a joyful spree,
Celebrating changes, oh so free! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range comments (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1)

Line range hint 134-138: Remove commented out redirectToLoginPage function.

This function appears to be unused and contains commented out code. Since the redirection logic is now handled in handleOnSubmit, this function is redundant.

Consider removing this unused function:

-  const redirectToLoginPage = () => {
-    // localStorage.clear();
-    // sessionStorage.clear();
-    history.push(`/${window?.contextPath}/citizen/login`);
-  };
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between f394ec7 and b237ffd.

📒 Files selected for processing (1)
  • micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1)

Pattern **/*.js: check

🔇 Additional comments (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/components/TopBarSideBar/SideBar/StaticCitizenSideBar.js (1)

97-106: Verify the impact of multiroot tenant check.

The new conditional logic for multiroot tenants affects the logout flow. Let's verify if this change is consistently handled across the application.

✅ Verification successful

Based on the search results, I can now generate the final response since I have enough information about how getMultiRootTenant() is used across the codebase and the logout implementation patterns.

The multiroot tenant logout handling is correctly implemented

The search results show that:

  • The logout implementation with multiroot tenant check is unique to this location and appropriately handles the redirection
  • Other uses of getMultiRootTenant() across the codebase are primarily for:
    • Tenant/state ID selection
    • UI component visibility control
    • Form field behavior
    • Data fetching configurations

The conditional logic for multiroot tenant logout is specific to the authentication flow and doesn't need to be replicated elsewhere since:

  1. This is the main logout handler in the application
  2. Other instances of window.location.href with login are for different purposes (checking current URL)
  3. The logout flow naturally belongs in the sidebar component where it's implemented
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other logout implementations that might need similar multiroot tenant handling
rg -l "Digit\.UserService\.logout" | xargs rg "window\.location\.href.*login"

# Search for other uses of getMultiRootTenant to ensure consistent behavior
rg "getMultiRootTenant"

Length of output: 12079

@jagankumar-egov jagankumar-egov merged commit ef8606f into develop Oct 23, 2024
3 checks passed
@jagankumar-egov jagankumar-egov deleted the citizen-redirect-logout branch October 23, 2024 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants